[pull] main from tinacms:main - #309
Merged
Merged
Conversation
Closes #7446 **TL;DR** `@tinacms/cli` currently ships a vulnerable js-yaml. One specifier change moves it to the patch on its own major line. **Pain:** GHSA-5p4m-2wfm-xmqj (high) covers both major lines, `>= 3.0.0 < 3.15.1` patched by 3.15.1 and `>= 4.0.0 < 4.3.1` patched by 4.3.1. #7425 closed the 3.x side by moving `@tinacms/graphql` to 3.15.1, which makes the repo look addressed, but `@tinacms/cli` was left on 4.1.1, inside the vulnerable 4.x range. js-yaml is a runtime `dependencies` entry there and the package is published, so `npm install @tinacms/cli` pulls a vulnerable copy today. Neither CI nor `dependency-review` flagged it, since the 4.x version was already present on `main` rather than introduced by a diff. **Solution:** Sets the specifier to `^4.3.1`, resolving 4.3.1. Afterwards no workspace package sits on a vulnerable js-yaml. A transitive 4.1.1 remains via `astro`, `cosmiconfig` and `eslint`, which is upstream of this repo and out of scope here. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Closes #7453 **TL;DR** #7447 fixed the vulnerable js-yaml but merged without a changeset, so the fix is sitting on `main` unreleased. This adds one. **Pain:** `@tinacms/cli` is published and not in the changesets `ignore` list, so a dependency change there needs a changeset to produce a version bump and a release. #7447 moved it from the vulnerable js-yaml 4.1.1 to 4.3.1, closing GHSA-5p4m-2wfm-xmqj on `main`, but with no changeset there is no release. The published package keeps resolving 4.1.1, so `npm install @tinacms/cli` still pulls the vulnerable copy and the advisory stays open for users. **Solution:** Adds a changeset marking `@tinacms/cli` `patch` and naming the js-yaml bump with its advisory. Version Packages #7443 is still open, so this is picked up in the current release rather than the one after. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Closes #7455 **TL;DR** #7425 and #7321 merged without changesets, so both fixes are stranded on `main`. This adds them. **Pain:** `@tinacms/graphql` and `tinacms-authjs` are both published and neither is in the changesets `ignore` list, so a dependency change in either needs a changeset to produce a version bump and a release. #7425 moved `@tinacms/graphql` to js-yaml 3.15.1 and #7321 moved `tinacms-authjs` to next-auth 4.24.15, both without one. The js-yaml case matters most: it closed GHSA-5p4m-2wfm-xmqj on the 3.x line, and `@tinacms/graphql` is the package that parses content YAML, so the published package still resolves the vulnerable 3.14.2 until a release ships. **Solution:** Adds a changeset for each, both `patch`, naming the bump and its advisory where there is one. Version Packages #7443 is still open, so these are picked up in the current release rather than the one after. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Bumps [tar](https://github.com/isaacs/node-tar) from 7.5.21 to 7.5.22. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/isaacs/node-tar/commit/2a22bfc5d3a432a606d9da0e2d87ba634aa3b1cb"><code>2a22bfc</code></a> 7.5.22</li> <li><a href="https://github.com/isaacs/node-tar/commit/df1cd8dc09cded47b00c4129698824b3986432ac"><code>df1cd8d</code></a> Allow transform to be falsey</li> <li>See full diff in <a href="https://github.com/isaacs/node-tar/compare/v7.5.21...v7.5.22">compare view</a></li> </ul> </details> <br /> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: kulesy <kulewidak@gmail.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: Eli Kent [SSW] <69125238+kulesy@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )